Skip to content

ENG-6115: use case page#1413

Merged
Alek99 merged 13 commits intomainfrom
ahmad/use-case-landing
Jun 10, 2025
Merged

ENG-6115: use case page#1413
Alek99 merged 13 commits intomainfrom
ahmad/use-case-landing

Conversation

@LineIndent
Copy link
Copy Markdown
Contributor

No description provided.

@linear
Copy link
Copy Markdown

linear bot commented Jun 5, 2025

Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

Added a new use case page to showcase Reflex's applications across different industries, with comprehensive markdown content and proper website integration.

  • Created pcweb/pages/use_case/use_case.py implementing a standard layout with navigation and content sections
  • Added industry-specific use cases in pcweb/pages/use_case/use-case.md covering financial services, e-commerce, DevOps, and AI workflows
  • Identified duplicate imports in pcweb/pages/__init__.py that need cleanup for better maintainability
  • Ensure consistent file naming: use_case.py vs use-case.md should follow the same convention

💡 (4/5) You can add custom instructions or style guidelines for the bot here!

3 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile

@tgberkeley
Copy link
Copy Markdown
Collaborator

Screenshot 2025-06-05 at 10 11 39 AM

Let's move the image to be below the heading and above the text for all of the sections

@tgberkeley
Copy link
Copy Markdown
Collaborator

Let's also add more space within and most importantly between the sections so it doesn't look as dense. Right now it looks a little too squeezed together

@tgberkeley
Copy link
Copy Markdown
Collaborator

Screenshot 2025-06-05 at 10 27 45 AM
We also need to add this page to the company section here so people can find it

@LineIndent
Copy link
Copy Markdown
Contributor Author

@tgberkeley made the fixes for the docs - the inner spacing between paragraphs is already set (and. consistent across the other markdowns), but I added spaces between sections and numbered them to improve readability

@Alek99
Copy link
Copy Markdown
Member

Alek99 commented Jun 6, 2025

Can you put it in the doc page instead
Screenshot 2025-06-05 at 5 35 59 PM

Also we should duplicate the page to be at the end of the getting started in framework section.

Copy link
Copy Markdown
Member

@Alek99 Alek99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok we can remove the non doc page for the use cases - I dont like how the logic is duplicated in two exact same files but maybe there is not a good solution right now.

But we should get rid of the non doc page one and link the navbar to the ai builder page use case

@LineIndent LineIndent changed the title [ENG-6115] use case page ENG-6115: use case page Jun 10, 2025
@Alek99 Alek99 self-requested a review June 10, 2025 21:54
@Alek99 Alek99 merged commit 2f6cb83 into main Jun 10, 2025
8 checks passed
@Alek99 Alek99 deleted the ahmad/use-case-landing branch June 10, 2025 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants